home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941031-19941221
/
000390_news@columbia.edu_Sun Dec 11 04:40:27 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA26787
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 11 Dec 1994 13:02:08 -0500
Received: by apakabar.cc.columbia.edu id AA03825
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 11 Dec 1994 13:02:07 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: 3.14 beta 14 and PC/TCP
Message-Id: <1994Dec11.104027.35139@cc.usu.edu>
Date: 11 Dec 94 10:40:27 MDT
References: <D0n8CD.Gn8@adasoft.ch>
Organization: Utah State University
Lines: 36
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <D0n8CD.Gn8@adasoft.ch>, jw@adasoft.ch (Jamie Watson) writes:
>
> I must be doing something wrong, but I can't figure out what...
>
> I am trying to use 3.14 Beta-14 with FTP Software PC/TCP 3.0 to connect
> from my laptop to my Unix system. The laptop is a Toshiba 1950CS, with
> a Xircom PCMCIA ethernet adapter. The Unix system is a DECsystem 5000/50,
> running Ultrix 4.4.
>
> When I first start the system, I can reach the Ultrix system with all of
> the normal PC/TCP utilities (ping, tn, rlogin, etc). I then start kermit,
> and give it what I think are the minimum configuration commands to get it
> working over TCP/IP:
>
> set tcp addr 193.72.200.10
> set tcp host 193.72.200.7
> con
>
> It connects, and everything seems just fine. But after I log out, and
> terminate kermit, none of the PC/TCP utilities work any more! If I try
> to ping the Unix system, I get "ARP failed", and nothing I have tried can
> get this working again, short of rebooting the laptop. But if I start
> kermit again, I can still connect to the Unix system! I'm really very
> confused...
--------------
The situation is easy to clarify. SET PORT TCP in Kermit means
to use Kermit's internal TCP/IP stack. That stack requires either a suitable
Packet Driver or ODI to talk to the lan adapter. FTP Inc's stack does more
or less the same thing. You loaded FTP Inc's stack and then told Kermit to
go to the same board and grab it; you are not running "over FTP Inc's stack."
I'm surprized that you we able to run Kermit over the board with FTP still
using all the TCP/IP material.
If you want FTP Inc's stack to remain resident and run Kermit
over the top of it you must use FTP's TNGLASS program, and tell Kermit
SET PORT BIOS1.
Joe D.